翻訳と辞書
Words near each other
・ Real-time database
・ Real-time Delphi
・ Real-time economy
・ Real-time enterprise
・ Real-time geotagging
・ Real-time gross settlement
・ Real-time Labor Market Information
・ Real-time large-scale change
・ Real-time locating system
・ Real-time marketing
・ Real-time MRI
・ Real-time multimedia over ATM
・ Real-Time Multiprogramming Operating System
・ Real-time Neutron Monitor Database
・ Real-Time Object-Oriented Modeling
Real-time operating system
・ Real-time outbreak and disease surveillance
・ Real-time polymerase chain reaction
・ Real-time posting
・ Real-time Programming Language
・ Real-Time Publish-Subscribe (RTPS) Protocol
・ Real-time recovery
・ Real-time rendering
・ Real-time ridesharing
・ Real-time simulation
・ Real-time sociolinguistics
・ Real-time strategy
・ Real-Time Systems (company)
・ Real-time tactics
・ Real-time testing


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Real-time operating system : ウィキペディア英語版
Real-time operating system
A real-time operating system (RTOS) is an operating system (OS) intended to serve real-time application process data as it comes in, typically without buffering delays. Processing time requirements (including any OS delay) are measured in tenths of seconds or shorter.
A key characteristic of an RTOS is the level of its consistency concerning the amount of time it takes to accept and complete an application's task; the variability is ''jitter''. A ''hard'' real-time operating system has less jitter than a ''soft'' real-time operating system. The chief design goal is not high throughput, but rather a guarantee of a soft or hard performance category. An RTOS that can usually or ''generally'' meet a ''deadline'' is a soft real-time OS, but if it can meet a deadline deterministically it is a hard real-time OS.
An RTOS has an advanced algorithm for scheduling. Scheduler flexibility enables a wider, computer-system orchestration of process priorities, but a real-time OS is more frequently dedicated to a narrow set of applications. Key factors in a real-time OS are minimal interrupt latency and minimal thread switching latency; a real-time OS is valued more for how quickly or how predictably it can respond than for the amount of work it can perform in a given period of time.
== Design philosophies ==

The most common designs are:
* Event-driven which switches tasks only when an event of higher priority needs servicing, called preemptive priority, or priority scheduling.
* Time-sharing designs switch tasks on a regular clocked interrupt, and on events, called round robin.
Time sharing designs switch tasks more often than strictly needed, but give smoother multitasking, giving the illusion that a process or user has sole use of a machine.
Early CPU designs needed many cycles to switch tasks, during which the CPU could do nothing else useful. For example, with a 20 MHz 68000 processor (typical of the late 1980s), task switch times are roughly 20 microseconds. (In contrast, a 100 MHz ARM CPU (from 2008) switches in less than 3 microseconds.)〔(【引用サイトリンク】 Context switching time )〕 Because of this, early OSes tried to minimize wasting CPU time by avoiding unnecessary task switching.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Real-time operating system」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.